Associating playback devices with playback queues

ABSTRACT

An example first playback device includes programming to perform functions including receiving a first request to associate with a first playback queue that is stored remotely from, and persists unassociated with, any playback device of the media playback system. The functions also include associating with the first playback queue and designating the first playback queue as an active queue of the first playback device. The functions also include receiving a second request to enter into a group with a second playback device that is associated with a second playback queue, entering into the group with the second playback device, associating with the second playback queue, and designating the second playback queue as the active queue of the first playback device. The functions also include receiving a third request to leave the group, and after receiving the third request, de-designating the second playback queue as its active queue.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. non-provisional patentapplication Ser. No. 14/855,695, filed on Sep. 16, 2015, entitled“Associating Playback Devices with Playback Queues,” which is acontinuation of U.S. non-provisional patent application Ser. No.13/944,702, filed on Jul. 17, 2013, entitled “Associating PlaybackDevices with Playback Queues,” both of which are incorporated herein byreference in their entirety.

FIELD OF THE DISCLOSURE

The disclosure is related to consumer goods and, more particularly, tomethods, systems, products, features, services, and other items directedto media playback or some aspect thereof.

BACKGROUND

Digital music has become readily available due in part to thedevelopment of consumer level technology that has allowed people tolisten to digital music on a personal audio device. The consumer'sincreasing preference for digital audio has also resulted in theintegration of personal audio devices into PDAs, cellular phones, andother mobile devices. The portability of these mobile devices hasenabled people to take the music listening experience with them andoutside of the home. People have become able to consume digital music,like digital music files or even Internet radio, in the home through theuse of their computer or similar devices. Now there are many differentways to consume digital music, in addition to other digital contentincluding digital video and photos, stimulated in many ways byhigh-speed Internet access at home, mobile broadband Internet access,and the consumer's hunger for digital media.

Until recently, options for accessing and listening to digital audio inan out-loud setting were severely limited. In 2005, Sonos offered forsale its first digital audio system that enabled people to, among manyother things, access virtually unlimited sources of audio via one ormore networked connected zone players, dynamically group or ungroup zoneplayers upon command, wirelessly send the audio over a local networkamongst zone players, and play the digital audio out loud in synchrony.The Sonos system can be controlled by software applications downloadedto certain network capable, mobile devices and computers.

Given the insatiable appetite of consumers towards digital media, therecontinues to be a need to develop consumer technology thatrevolutionizes the way people access and consume digital media.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and advantages of the presently disclosed technologymay be better understood with regard to the following description,appended claims, and accompanying drawings where:

FIG. 1 shows an example configuration in which certain embodiments maybe practiced;

FIG. 2A shows an illustration of an example zone player having abuilt-in amplifier and transducers;

FIG. 2B shows an illustration of an example zone player having abuilt-in amplifier and connected to external speakers;

FIG. 2C shows an illustration of an example zone player connected to anA/V receiver and speakers;

FIG. 3 shows an illustration of an example controller;

FIG. 4 shows an internal functional block diagram of an example zoneplayer;

FIG. 5 shows an internal functional block diagram of an examplecontroller;

FIG. 6 shows an example network for media content playback;

FIG. 7 shows an example ad-hoc playback network;

FIG. 8 shows a system including a plurality of networks including acloud-based network and at least one local playback network;

FIG. 9 illustrates a flow diagram of an example method to associate aplayback device with a playback queue;

FIG. 10 illustrates a flow diagram of an example method to maintain andassociate a playback device with at least one of a saved playback queueor a group queue;

FIG. 11 shows an example system including a plurality of playback queuesand at least one associated example zone player.

In addition, the drawings are for the purpose of illustrating exampleembodiments, but it is understood that the inventions are not limited tothe arrangements and instrumentality shown in the drawings.

DETAILED DESCRIPTION I. Overview

A media playback device may be configured to play audio content from aplayback queue associated with or assigned to the playback device. Insome examples, the playback device may be grouped with another playbackdevice to play audio in synchrony, and in some examples, a playbackqueue is associated with or assigned to the group. At some point, theplayback device may be removed from the group. Upon removal of theplayback device from the group, a user may wish to play audio from theplayback device, either at the time of removal from the group or at alater time, without manually reassigning the playback device to aplayback queue.

Creation of playback queues is an important element in playing audiofrom a playback device or a group of playback devices. In some examples,a user may create a playback queue and assign a playback device (orgroup of playback devices) to the playback queue at the time of creationof the playback queue. In other examples, a user may create a playbackqueue, however, the user may choose not to assign a playback device (orgroup of playback devices) to the playback queue until a later time suchthat the playback queue persists without being assigned to a playbackdevice (or group of playback devices).

Example methods, apparatus, systems, and articles of manufacturedisclosed herein enable a playback device to automatically associatewith a playback queue such that the playback device is continuouslyenabled to play content from a playback queue. For example, a playbackdevice may associate with a first playback queue. At some future pointin time, the playback device may link to a group of playback devicessuch that the playback device plays content from a second playback queuethat is associated with the group. In some examples, the playback devicemay maintain an association with the first playback queue while it is inthe group. For as long as the playback device is in the group, theplayback device may be selectively removed from the group. Upon removalfrom the group, the playback device is automatically associated with aplayback queue. In some examples, the playback device may restore thefirst playback queue, maintain the association with the second playbackqueue, and/or associate with a new playback queue. Further examplesdisclosed herein provide for the creation and persistence of playbackqueues without an association to a playback device or group of playbackdevices. Example methods and apparatus disclosed herein mayadvantageously provide for improved usability of a playback device upondissociation of the playback device from a networked group as well asimproved configurability of playback queues.

Other embodiments, as those discussed in the following and others as canbe appreciated by one having ordinary skill in the art are alsopossible.

II. Example Operating Environment

Referring now to the drawings, in which like numerals can refer to likeparts throughout the figures, FIG. 1 shows an example media systemconfiguration 100 in which one or more embodiments disclosed herein canbe practiced or implemented.

By way of illustration, the media system configuration 100 is associatedwith a home having multiple zones, though the home could have beenconfigured with only one zone. Additionally, one or more zones can beadded over time. Each zone may be assigned by a user to a different roomor space, such as, for example, an office, bathroom, bedroom, kitchen,dining room, family room, home theater room, utility or laundry room,and patio. A single zone might also include multiple rooms or spaces ifso configured. With respect to FIG. 1, one or more of zone players102-124 are shown in each respective zone. A zone player 102-124, alsoreferred to herein as a playback device, multimedia unit, speaker,player, and so on, provides audio, video, and/or audiovisual output. Acontroller 130 (e.g., shown in the kitchen for purposes of thisillustration) provides control to the media system configuration 100.Controller 130 may be fixed to a zone, or alternatively, mobile suchthat it can be moved about the zones. The media system configuration 100may also include more than one controller 130, and additionalcontrollers may be added to the system over time.

The media system configuration 100 illustrates an example whole housemedia system, though it is understood that the technology describedherein is not limited to, among other things, its particular place ofapplication or to an expansive system like a whole house media system100 of FIG. 1.

a) Example Zone Players

FIGS. 2A, 2B, and 2C show example types of zone players. Zone players200, 202, and 204 of FIGS. 2A, 2B, and 2C, respectively, can correspondto any of the zone players 102-124 of FIG. 1, for example. In someembodiments, audio is reproduced using only a single zone player, suchas by a full-range player. In some embodiments, audio is reproducedusing two or more zone players, such as by using a combination offull-range players or a combination of full-range and specializedplayers. In some embodiments, zone players 200-204 may also be referredto as a “smart speaker,” because they contain processing capabilitiesbeyond the reproduction of audio, more of which is described below.

FIG. 2A illustrates zone player 200 that includes sound producingequipment 208 capable of reproducing full-range sound. The sound maycome from an audio signal that is received and processed by zone player200 over a wired or wireless data network. Sound producing equipment 208includes one or more built-in amplifiers and one or more acoustictransducers (e.g., speakers). A built-in amplifier is described morebelow with respect to FIG. 4. A speaker or acoustic transducer caninclude, for example, any of a tweeter, a mid-range driver, a low-rangedriver, and a subwoofer. In some embodiments, zone player 200 can bestatically or dynamically configured to play stereophonic audio,monaural audio, or both. In some embodiments, zone player 200 may bedynamically configured to reproduce a subset of full-range sound, suchas when zone player 200 is grouped with other zone players to playstereophonic audio, monaural audio, and/or surround audio or when theaudio content received by zone player 200 is less than full-range.

FIG. 2B illustrates zone player 202 that includes a built-in amplifierto power a set of detached speakers 210. A detached speaker can include,for example, any type of loudspeaker. Zone player 202 may be configuredto power one, two, or more separate loudspeakers. Zone player 202 may beconfigured to communicate an audio signal (e.g., right and left channelaudio or more channels depending on its configuration) to the detachedspeakers 210 via a wired path.

FIG. 2C illustrates zone player 204 that does not include a built-inamplifier, but is configured to communicate an audio signal, receivedover a data network, to an audio (or “audio/video”) receiver 214 withbuilt-in amplification.

Referring back to FIG. 1, in some embodiments, one, some, or all of thezone players 102 to 124 can retrieve audio directly from a source. Forexample, a particular zone player in a zone or zone group may beassigned to a playback queue (or “queue”). The playback queue containsinformation corresponding to zero or more audio items for playback bythe associated zone or zone group. The playback queue may be stored inmemory on a zone player or some other designated device. Each itemcontained in the playback queue may comprise a uniform resourceidentifier (URI) or some other identifier that can be used by the zoneplayer(s) to seek out and/or retrieve the audio items from theidentified audio source(s). Depending on the item, the audio sourcemight be found on the Internet (e.g., the cloud), locally from anotherdevice over the data network 128 (described further below), from thecontroller 130, stored on the zone player itself, or from an audiosource communicating directly to the zone player. In some embodiments,the zone player can reproduce the audio itself (e.g., play the audio),send the audio to another zone player for reproduction, or both wherethe audio is reproduced by the zone player as well as one or moreadditional zone players (possibly in synchrony). In some embodiments,the zone player may play a first audio content (or alternatively, maynot play the content at all), while sending a second, different audiocontent to another zone player(s) for reproduction. To the user, eachitem in a playback queue is represented on an interface of a controllerby an element such as a track name, album name, playlist, or other someother representation. A user can populate the playback queue with audioitems of interest. The user may also modify and clear the playbackqueue, if so desired.

By way of illustration, SONOS, Inc. of Santa Barbara, Calif. presentlyoffers for sale zone players referred to as a “PLAY:5,” “PLAY:3,”“PLAYBAR,” “CONNECT:AMP,” “CONNECT,” and “SUB.” Any other past, present,and/or future zone players can additionally or alternatively be used toimplement the zone players of example embodiments disclosed herein.Additionally, it is understood that a zone player is not limited to theparticular examples illustrated in FIGS. 2A, 2B, and 2C or to the SONOSproduct offerings. For example, a zone player may include a wired orwireless headphone. In yet another example, a zone player might includea sound bar for television. In yet another example, a zone player mayinclude or interact with a docking station for an Apple IPOD™ or similardevice.

b. Example Controllers

FIG. 3 illustrates an example wireless controller 300 in docking station302. By way of illustration, controller 300 may correspond tocontrolling device 130 of FIG. 1. Docking station 302, if provided orused, may provide power to the controller 300 and additionally maycharge a battery of controller 300. In some embodiments, controller 300may be provided with a touch screen 304 that allows a user to interactthrough touch with the controller 300, for example, to retrieve andnavigate a playlist of audio items, control operations of one or morezone players, and provide overall control of the system configuration100. In other embodiments, other input mechanisms such as voice controlmay be used to interact with the controller 300. In certain embodiments,any number of controllers can be used to control the systemconfiguration 100. In some embodiments, there may be a limit set on thenumber of controllers that can control the system configuration 100. Thecontrollers might be wireless like wireless controller 300 or wired todata network 128.

In some embodiments, if more than one controller is used in system 100of FIG. 1, each controller may be coordinated to display common content,and may all be dynamically updated to indicate changes made to thesystem 100 from a single controller. Coordination can occur, forinstance, by a controller periodically requesting a state variabledirectly or indirectly from one or more of the zone players; the statevariable may provide information about system 100, such as current zonegroup configuration, what is playing in one or more zones, volumelevels, and other items of interest. The state variable may be passedaround on data network 128 between zone players (and controllers, if sodesired) as needed or as often as programmed.

In addition, an application running on any network-enabled portabledevice, such as an IPHONE™, IPAD™, ANDROID™ powered phone or tablet, orany other smart phone or network-enabled device can be used ascontroller 130. An application running on a laptop or desktop personalcomputer (PC) or Mac™ can also be used as controller 130. Suchcontrollers may connect to system 100 through an interface with datanetwork 128, a zone player, a wireless router, or using some otherconfigured connection path. Example controllers offered by Sonos, Inc.of Santa Barbara, Calif. include a “Controller 200,” “SONOS® CONTROL,”“SONOS® Controller for IPHONE™,” “SONOS® Controller for IPAD™,” “SONOS®Controller for ANDROID™,” “SONOS® Controller for MAC™ or PC.”

c. Example Data Connection

Zone players 102 to 124 of FIG. 1 are coupled directly or indirectly toa data network, such as data network 128. Controller 130 may also becoupled directly or indirectly to data network 128 or individual zoneplayers. Data network 128 is represented by an octagon in the figure tostand out from other representative components. While data network 128is shown in a single location, it is understood that such a network isdistributed in and around system 100. Particularly, data network 128 canbe a wired network, a wireless network, or a combination of both wiredand wireless networks. In some embodiments, one or more of the zoneplayers 102-124 are wirelessly coupled to data network 128 based on aproprietary mesh network. In some embodiments, one or more of the zoneplayers are coupled to data network 128 using a centralized access pointsuch as a wired or wireless router. In some embodiments, one or more ofthe zone players 102-124 are coupled via a wire to data network 128using Ethernet or similar technology. In addition to the one or morezone players 102-124 connecting to data network 128, data network 128can further allow access to a wide area network, such as the Internet.

In some embodiments, connecting any of the zone players 102-124, or someother connecting device, to a broadband router, can create data network128. Other zone players 102-124 can then be added wired or wirelessly tothe data network 128. For example, a zone player (e.g., any of zoneplayers 102-124) can be added to the system configuration 100 by simplypressing a button on the zone player itself (or perform some otheraction), which enables a connection to be made to data network 128. Thebroadband router can be connected to an Internet Service Provider (ISP),for example. The broadband router can be used to form another datanetwork within the system configuration 100, which can be used in otherapplications (e.g., web surfing). Data network 128 can also be used inother applications, if so programmed. An example, second network mayimplement SONOSNET™ protocol, developed by SONOS, Inc. of Santa Barbara.SONOSNET™ represents a secure, AES-encrypted, peer-to-peer wireless meshnetwork. Alternatively, in certain embodiments, the data network 128 isthe same network, such as a traditional wired or wireless network, usedfor other applications in the household.

d. Example Zone Configurations

A particular zone can contain one or more zone players. For example, thefamily room of FIG. 1 contains two zone players 106 and 108, while thekitchen is shown with one zone player 102. In another example, the hometheater room contains additional zone players to play audio from a 5.1channel or greater audio source (e.g., a movie encoded with 5.1 orgreater audio channels). In some embodiments, one can position a zoneplayer in a room or space and assign the zone player to a new orexisting zone via controller 130. As such, zones may be created,combined with another zone, removed, and given a specific name (e.g.,“Kitchen”), if so desired and programmed to do so with controller 130.Moreover, in some embodiments, zone configurations may be dynamicallychanged even after being configured using controller 130 or some othermechanism.

In some embodiments, a “bonded zone” is a zone that contains two or morezone players, such as the two zone players 106 and 108 in the familyroom, whereby the two zone players 106 and 108 can be configured to playthe same audio source in synchrony. In one example, the two zone players106 and 108 can be paired to play two separate sounds in left and rightchannels, for example. In other words, the stereo effects of a sound canbe reproduced or enhanced through the two zone players 106 and 108, onefor the left sound and the other for the right sound. In anotherexample, two or more zone players can be sonically consolidated to forma single, consolidated zone player. A consolidated zone player (thoughmade up of multiple, separate devices) can be configured to process andreproduce sound differently than an unconsolidated zone player or zoneplayers that are paired, because a consolidated zone player hasadditional speaker drivers from which sound can be passed. Theconsolidated zone player can further be paired with a single zone playeror yet another consolidated zone player. Each playback device of aconsolidated playback device can be set in a consolidated mode, forexample.

In certain embodiments, paired or consolidated zone players (alsoreferred to as “bonded zone players”) can play audio in synchrony withother zone players in the same or different zones.

According to some embodiments, one can continue to do any of: group,consolidate, and pair zone players, for example, until a desiredconfiguration is complete. The actions of grouping, consolidation, andpairing are preferably performed through a control interface, such asusing controller 130, and not by physically connecting and re-connectingspeaker wire, for example, to individual, discrete speakers to createdifferent configurations. As such, certain embodiments described hereinprovide a more flexible and dynamic platform through which soundreproduction can be offered to the end-user.

e. Example Audio Sources

In some embodiments, each zone can play from the same audio source asanother zone or each zone can play from a different audio source. Forexample, someone can be grilling on the patio and listening to jazzmusic via zone player 124, while someone is preparing food in thekitchen and listening to classical music via zone player 102. Further,someone can be in the office listening to the same jazz music via zoneplayer 110 that is playing on the patio via zone player 124. In someembodiments, the jazz music played via zone players 110 and 124 isplayed in synchrony. Synchronizing playback amongst zones allows forsomeone to pass through zones while seamlessly (or substantiallyseamlessly) listening to the audio. Further, zones can be put into a“party mode” such that all associated zones will play audio insynchrony.

Sources of audio content to be played by zone players 102-124 arenumerous. In some embodiments, audio on a zone player itself may beaccessed and played. In some embodiments, audio on a controller may beaccessed via the data network 128 and played. In some embodiments, musicfrom a personal library stored on a computer or networked-attachedstorage (NAS) may be accessed via the data network 128 and played. Insome embodiments, Internet radio stations, shows, and podcasts may beaccessed via the data network 128 and played. Music or cloud servicesthat let a user stream and/or download music and audio content may beaccessed via the data network 128 and played. Further, music may beobtained from traditional sources, such as a turntable or CD player, viaa line-in connection to a zone player, for example. Audio content mayalso be accessed using a different protocol, such as AIRPLAY™, which isa wireless technology by Apple, Inc., for example. Audio contentreceived from one or more sources can be shared amongst the zone players102 to 124 via data network 128 and/or controller 130. Theabove-disclosed sources of audio content are referred to herein asnetwork-based audio information sources. However, network-based audioinformation sources are not limited thereto.

In some embodiments, the example home theater zone players 116, 118, 120are coupled to an audio information source such as a television 132. Insome examples, the television 132 is used as a source of audio for thehome theater zone players 116, 118, 120, while in other examples audioinformation from the television 132 may be shared with any of the zoneplayers 102-124 in the audio system 100.

III. Example Zone Players

Referring now to FIG. 4, there is shown an example block diagram of azone player 400 in accordance with an embodiment. Zone player 400includes a network interface 402, a processor 408, a memory 410, anaudio processing component 412, one or more modules 414, an audioamplifier 416, and a speaker unit 418 coupled to the audio amplifier416. FIG. 2A shows an example illustration of such a zone player. Othertypes of zone players may not include the speaker unit 418 (e.g., suchas shown in FIG. 2B) or the audio amplifier 416 (e.g., such as shown inFIG. 2C). Further, it is contemplated that the zone player 400 can beintegrated into another component. For example, the zone player 400could be constructed as part of a television, lighting, or some otherdevice for indoor or outdoor use.

In some embodiments, network interface 402 facilitates a data flowbetween zone player 400 and other devices on a data network 128. In someembodiments, in addition to getting audio from another zone player ordevice on data network 128, zone player 400 may access audio directlyfrom the audio source, such as over a wide area network or on the localnetwork. In some embodiments, the network interface 402 can furtherhandle the address part of each packet so that it gets to the rightdestination or intercepts packets destined for the zone player 400.Accordingly, in certain embodiments, each of the packets includes anInternet Protocol (IP)-based source address as well as an IP-baseddestination address.

In some embodiments, network interface 402 can include one or both of awireless interface 404 and a wired interface 406. The wireless interface404, also referred to as a radio frequency (RF) interface, providesnetwork interface functions for the zone player 400 to wirelesslycommunicate with other devices (e.g., other zone player(s), speaker(s),receiver(s), component(s) associated with the data network 128, and soon) in accordance with a communication protocol (e.g., any wirelessstandard including IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.15, 4Gmobile communication standard, and so on). Wireless interface 404 mayinclude one or more radios. To receive wireless signals and to providethe wireless signals to the wireless interface 404 and to transmitwireless signals, the zone player 400 includes one or more antennas 420.The wired interface 406 provides network interface functions for thezone player 400 to communicate over a wire with other devices inaccordance with a communication protocol (e.g., IEEE 802.3). In someembodiments, a zone player includes multiple wireless 404 interfaces. Insome embodiments, a zone player includes multiple wired 406 interfaces.In some embodiments, a zone player includes both of the interfaces 404and 406. In some embodiments, a zone player 400 includes only thewireless interface 404 or the wired interface 406.

In some embodiments, the processor 408 is a clock-driven electronicdevice that is configured to process input data according toinstructions stored in memory 410. The memory 410 is data storage thatcan be loaded with one or more software module(s) 414, which can beexecuted by the processor 408 to achieve certain tasks. In theillustrated embodiment, the memory 410 is a tangible machine-readablemedium storing instructions that can be executed by the processor 408.In some embodiments, a task might be for the zone player 400 to retrieveaudio data from another zone player or a device on a network (e.g.,using a uniform resource locator (URL) or some other identifier). Insome embodiments, a task may be for the zone player 400 to send audiodata to another zone player or device on a network. In some embodiments,a task may be for the zone player 400 to synchronize playback of audiowith one or more additional zone players. In some embodiments, a taskmay be to pair the zone player 400 with one or more zone players tocreate a multi-channel audio environment. Additional or alternativetasks can be achieved via the one or more software module(s) 414 and theprocessor 408.

The audio processing component 412 can include one or moredigital-to-analog converters (DAC), an audio preprocessing component, anaudio enhancement component or a digital signal processor, and so on. Insome embodiments, the audio processing component 412 may be part ofprocessor 408. In some embodiments, the audio that is retrieved via thenetwork interface 402 is processed and/or intentionally altered by theaudio processing component 412. Further, the audio processing component412 can produce analog audio signals. The processed analog audio signalsare then provided to the audio amplifier 416 for playback throughspeakers 418. In addition, the audio processing component 412 caninclude circuitry to process analog or digital signals as inputs to playfrom zone player 400, send to another zone player on a network, or bothplay and send to another zone player on the network. An example inputincludes a line-in connection (e.g., an auto-detecting 3.5 mm audioline-in connection).

The audio amplifier 416 is a device(s) that amplifies audio signals to alevel for driving one or more speakers 418. The one or more speakers 418can include an individual transducer (e.g., a “driver”) or a completespeaker system that includes an enclosure including one or more drivers.A particular driver can be a subwoofer (e.g., for low frequencies), amid-range driver (e.g., for middle frequencies), and a tweeter (e.g.,for high frequencies), for example. An enclosure can be sealed orported, for example. Each transducer may be driven by its own individualamplifier.

A commercial example, presently known as the PLAY:5™, is a zone playerwith a built-in amplifier and speakers that is capable of retrievingaudio directly from the source, such as on the Internet or on the localnetwork, for example. In particular, the PLAY:5™ is a five-amp,five-driver speaker system that includes two tweeters, two mid-rangedrivers, and one woofer. When playing audio content via the PLAY:5, theleft audio data of a track is sent out of the left tweeter and leftmid-range driver, the right audio data of a track is sent out of theright tweeter and the right mid-range driver, and mono bass is sent outof the subwoofer. Further, both mid-range drivers and both tweeters havethe same equalization (or substantially the same equalization). That is,they are both sent the same frequencies but from different channels ofaudio. Audio from Internet radio stations, online music and videoservices, downloaded music, analog audio inputs, television, DVD, and soon, can be played from the PLAY:5™.

IV. Example Controller

Referring now to FIG. 5, there is shown an example block diagram forcontroller 500, which can correspond to the controlling device 130 inFIG. 1. Controller 500 can be used to facilitate the control ofmulti-media applications, automation and others in a system. Inparticular, the controller 500 may be configured to facilitate aselection of a plurality of audio sources available on the network andenable control of one or more zone players (e.g., the zone players102-124 in FIG. 1) through a wireless or wired network interface 508.According to one embodiment, the wireless communications is based on anindustry standard (e.g., infrared, radio, wireless standards includingIEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.15, 4G mobile communicationstandard, and so on). Further, when a particular audio is being accessedvia the controller 500 or being played via a zone player, a picture(e.g., album art) or any other data, associated with the audio and/oraudio source can be transmitted from a zone player or other electronicdevice to controller 500 for display.

Controller 500 is provided with a screen 502 and an input interface 514that allows a user to interact with the controller 500, for example, tonavigate a playlist of many multimedia items and to control operationsof one or more zone players. The screen 502 on the controller 500 can bean LCD screen, for example. The screen 500 communicates with and iscommanded by a screen driver 504 that is controlled by a microcontroller(e.g., a processor) 506. The memory 510 can be loaded with one or moreapplication modules 512 that can be executed by the microcontroller 506with or without a user input via the user interface 514 to achievecertain tasks. In some embodiments, an application module 512 isconfigured to facilitate grouping a number of selected zone players intoa zone group and synchronizing the zone players for audio playback. Insome embodiments, an application module 512 is configured to control theaudio sounds (e.g., volume) of the zone players in a zone group. Inoperation, when the microcontroller 506 executes one or more of theapplication modules 512, the screen driver 504 generates control signalsto drive the screen 502 to display an application specific userinterface accordingly.

The controller 500 includes a network interface 508 that facilitateswired or wireless communication with a zone player. In some embodiments,the commands such as volume control and audio playback synchronizationare sent via the network interface 508. In some embodiments, a savedzone group configuration is transmitted between a zone player and acontroller via the network interface 508. The controller 500 can controlone or more zone players, such as 102-124 of FIG. 1. There can be morethan one controller for a particular system, and each controller mayshare common information with another controller, or retrieve the commoninformation from a zone player, if such a zone player storesconfiguration data (e.g., such as a state variable). Further, acontroller can be integrated into a zone player.

It should be noted that other network-enabled devices such as an IPHONE™IPAD™ or any other smart phone or network-enabled device (e.g., anetworked computer such as a PC or MAC™) can also be used as acontroller to interact or control zone players in a particularenvironment. In some embodiments, a software application or upgrade canbe downloaded onto a network-enabled device to perform the functionsdescribed herein.

In certain embodiments, a user can create a zone group (also referred toas a bonded zone) including at least two zone players from thecontroller 500. The zone players in the zone group can play audio in asynchronized fashion, such that all of the zone players in the zonegroup playback an identical audio source or a list of identical audiosources in a synchronized manner such that no (or substantially no)audible delays or hiccups are to be heard. Similarly, in someembodiments, when a user increases the audio volume of the group fromthe controller 500, the signals or data of increasing the audio volumefor the group are sent to one of the zone players and causes other zoneplayers in the group to be increased together in volume.

A user via the controller 500 can group zone players into a zone groupby activating a “Link Zones” or “Add Zone” soft button, or de-grouping azone group by activating an “Unlink Zones” or “Drop Zone” button. Forexample, one mechanism for ‘joining’ zone players together for audioplayback is to link a number of zone players together to form a group.To link a number of zone players together, a user can manually link eachzone player or room one after the other. For example, assume that thereis a multi-zone system that includes the following zones: Bathroom,Bedroom, Den, Dining Room, Family Room, and Foyer.

In certain embodiments, a user can link any number of the six zoneplayers, for example, by starting with a single zone and then manuallylinking each zone to that zone.

In certain embodiments, a set of zones can be dynamically linkedtogether using a command to create a zone scene or theme (subsequent tofirst creating the zone scene). For instance, a “Morning” zone scenecommand can link the Bedroom, Office, and Kitchen zones together in oneaction. Without this single command, the user would manually andindividually link each zone. The single command may include a mouseclick, a double mouse click, a button press, a gesture, or some otherprogrammed or learned action. Other kinds of zone scenes can beprogrammed or learned by the system over time.

In certain embodiments, a zone scene can be triggered based on time(e.g., an alarm clock function). For instance, a zone scene can be setto apply at 8:00 am. The system can link appropriate zonesautomatically, set specific music to play, and then stop the music aftera defined duration. Although any particular zone can be triggered to an“On” or “Off” state based on time, for example, a zone scene enables anyzone(s) linked to the scene to play a predefined audio (e.g., afavorable song, a predefined playlist) at a specific time and/or for aspecific duration. If, for any reason, the scheduled music failed to beplayed (e.g., an empty playlist, no connection to a share, failedUniversal Plug and Play (UPnP), no Internet connection for an InternetRadio station, and so on), a backup buzzer can be programmed to sound.The buzzer can include a sound file that is stored in a zone player, forexample.

V. Playback Queue

As discussed above, in some embodiments, a zone player may be assignedto or otherwise associated with a playback queue identifying zero ormore media items for playback by the zone player. The media itemsidentified in a playback queue may be represented to the user via aninterface on a controller. For instance, the representation may show theuser (or users if more than one controller is connected to the system)how the zone player is traversing the playback queue, such as byhighlighting the “now playing” item, graying out the previously playeditem(s), highlighting the to-be-played item(s), and so on.

In some embodiments, a single zone player is assigned to a playbackqueue. For example, zone player 114 in the bathroom of FIG. 1 may belinked or assigned to a “Bathroom” playback queue. In an embodiment, the“Bathroom” playback queue might have been established by the system as aresult of the user naming the zone player 114 to the bathroom. As such,contents populated and identified in the “Bathroom” playback queue canbe played via the zone player 114 (the bathroom zone).

In some embodiments, a zone or zone group is assigned to a playbackqueue. For example, zone players 106 and 108 in the family room of FIG.1 may be linked or assigned to a “Family room” playback queue. Inanother example, if family room and dining room zones were grouped, thenthe new group would be linked or assigned to a “family room+dining room”playback queue. In some embodiments, the family room+dining roomplayback queue would be established based upon the creation of thegroup. In some embodiments, upon establishment of the new group, thefamily room+dining room playback queue can automatically include thecontents of one (or both) of the playback queues associated with eitherthe family room or dining room or both. In one instance, if the userstarted with the family room and added the dining room, then thecontents of the family room playback queue would become the contents ofthe family room+dining room playback queue. In another instance, if theuser started with the family room and added the dining room, then thefamily room playback queue would be renamed to the family room+diningroom playback queue. If the new group was “ungrouped,” then the familyroom+dining room playback queue may be removed from the system and/orrenamed to one of the zones (e.g., renamed to “family room” or “diningroom”). After ungrouping, each of the family room and the dining roomwill be assigned to a playback queue. In some examples, afterungrouping, the family room and the dining room are assigned todifferent playback queues having different audio content. In otherexamples, the family room and the dining room are assigned to the sameplayback queue or separate playback queues having the same orsubstantially the same audio content. In further examples, the familyroom and/or the dining room may be assigned to the “family room+diningroom” playback queue. One or more of the zone players in the zone orzone group may store in memory the associated playback queue.

As such, when zones or zone groups are “grouped” or “ungrouped”dynamically by the user via a controller, the system will, in someembodiments, establish or remove/rename playback queues respectively, aseach zone or zone group is to be assigned to a playback queue. In otherwords, the playback queue operates as a container that can be populatedwith media items for playback by the assigned zone. In some embodiments,the media items identified in a playback queue can be manipulated (e.g.,re-arranged, added to, deleted from, and so on).

By way of illustration, FIG. 6 shows an example network 600 for mediacontent playback. As shown, the example network 600 includes examplezone players 612 and 614, example audio sources 662 and 664, and examplemedia items 620. The example media items 620 may include playlist 622,music track 624, favorite Internet radio station 626, playlists 628 and630, and album 632. In one embodiment, the zone players 612 and 614 maybe any of the zone players shown in FIGS. 1, 2, and 4. For instance,zone players 612 and 614 may be the zone players 106 and 108 in theFamily Room.

In one example, the example audio sources 662 and 664, and example mediaitems 620 may be partially stored on a cloud network, discussed morebelow in connection to FIG. 8. In some cases, the portions of the audiosources 662, 664, and example media items 620 may be stored locally onone or both of the zone players 612 and 614. In one embodiment, playlist622, favorite Internet radio station 626, and playlist 630 may be storedlocally, and music track 624, playlist 628, and album 632 may be storedon the cloud network.

Each of the example media items 620 may be a list of media itemsplayable by a zone player(s). In one embodiment, the example media itemsmay be a collection of links or pointers (e.g., URI) to the underlyingdata for media items that are stored elsewhere, such as the audiosources 662 and 664. In another embodiment, the media items may includepointers to media content stored on the local zone player, another zoneplayer over a local network, or a controller device connected to thelocal network.

As shown, the example network 600 may also include an example queue 602associated with the zone player 612, and an example queue 604 associatedwith the zone player 614. Queue 606 may be associated with a group, whenin existence, comprising zone players 612 and 614. Queue 606 mightcomprise a new queue or exist as a renamed version of queue 602 or 604.In some embodiments, in a group, the zone players 612 and 614 would beassigned to queue 606 and queue 602 and 604 would not be available atthat time. In some embodiments, when the group is no longer inexistence, queue 606 is no longer available. In some embodiments, whenthe group is no longer in existence, queue 606 is assigned to zoneplayers 612 and/or 614. Each zone player and each combination of zoneplayers in a network of zone players, such as those shown in FIG. 1 orthat of example zone players 612, 614, and example combination 616, maybe associated with one or more corresponding playback queues.

A playback queue, such as playback queues 602, 604, 606, may includeidentification of media content to be played by the corresponding zoneplayer or combination of zone players. As such, media items added to theplayback queue are to be played by the corresponding zone player orcombination of zone players. The zone player may be configured to playitems in the queue according to a specific order (such as an order inwhich the items were added), in a random order, or in some other order.

The playback queue may include a combination of playlists and othermedia items added to the queue. In one embodiment, the items in playbackqueue 602 to be played by the zone player 612 may include items from theaudio sources 662, 664, or any of the media items 622-632. The playbackqueue 602 may also include items stored locally on the zone player 612,or items accessible from the zone player 614. For instance, the playbackqueue 602 may include Internet radio 626 and album 632 items from audiosource 662, and items stored on the zone player 612.

When a media item is added to the queue via an interface of acontroller, a link to the item may be added to the queue. In a case ofadding a playlist to the queue, links to the media items in the playlistmay be provided to the queue. For example, the playback queue 602 mayinclude pointers from the Internet radio 626 and album 632, pointers toitems on the audio source 662, and pointers to items on the zone player612. In another case, a link to the playlist, for example, rather than alink to the media items in the playlist may be provided to the queue,and the zone player or combination of zone players may play the mediaitems in the playlist by accessing the media items via the playlist. Forexample, the album 632 may include pointers to items stored on audiosource 662. Rather than adding links to the items on audio source 662, alink to the album 632 may be added to the playback queue 602, such thatthe zone player 612 may play the items on the audio source 662 byaccessing the items via pointers in the playlist 632.

In some cases, contents as they exist at a point in time within aplayback queue may be stored as a playlist, and subsequently added tothe same queue later or added to another queue. For example, contents ofthe playback queue 602, at a particular point in time, may be saved as aplaylist, stored locally on the zone player 612 and/or on the cloudnetwork. The saved playlist may then be added to playback queue 604 tobe played by zone player 614.

VI. Example Ad-Hoc Network

Particular examples are now provided in connection with FIG. 7 todescribe, for purposes of illustration, certain embodiments to provideand facilitate connection to a playback network. FIG. 7 shows that thereare three zone players 702, 704 and 706 and a controller 708 that form anetwork branch that is also referred to as an Ad-Hoc network 710. Thenetwork 710 may be wireless, wired, or a combination of wired andwireless technologies. In general, an Ad-Hoc (or “spontaneous”) networkis a local area network or other small network in which there isgenerally no one access point for all traffic. With an establishedAd-Hoc network 710, the devices 702, 704, 706 and 708 can allcommunicate with each other in a “peer-to-peer” style of communication,for example. Furthermore, devices may join and/or leave from the network710, and the network 710 will automatically reconfigure itself withoutneeding the user to reconfigure the network 710. While an Ad-Hoc networkis referenced in FIG. 7, it is understood that a playback network may bebased on a type of network that is completely or partially differentfrom an Ad-Hoc network.

Using the Ad-Hoc network 710, the devices 702, 704, 706, and 708 canshare or exchange one or more audio sources and be dynamically grouped(or ungrouped) to play the same or different audio sources. For example,the devices 702 and 704 are grouped to playback one piece of music, andat the same time, the device 706 plays back another piece of music. Inother words, the devices 702, 704, 706 and 708, as shown in FIG. 7, forma HOUSEHOLD that distributes audio and/or reproduces sound. As usedherein, the term HOUSEHOLD (provided in uppercase letters todisambiguate from the user's domicile) is used to represent a collectionof networked devices that are cooperating to provide an application orservice. An instance of a HOUSEHOLD is identified with a household 710(or household identifier), though a HOUSEHOLD may be identified with adifferent area or place.

In certain embodiments, a household identifier (HHID) is a short stringor an identifier that is computer-generated to help ensure that it isunique. Accordingly, the network 710 can be characterized by a uniqueHHID and a unique set of configuration variables or parameters, such aschannels (e.g., respective frequency bands), service set identifier(SSID) (a sequence of alphanumeric characters as a name of a wirelessnetwork), and WEP keys (wired equivalent privacy) or other securitykeys. In certain embodiments, SSID is set to be the same as HHID.

In certain embodiments, each HOUSEHOLD includes two types of networknodes: a control point (CP) and a zone player (ZP). The control pointcontrols an overall network setup process and sequencing, including anautomatic generation of required network parameters (e.g., securitykeys). In an embodiment, the CP also provides the user with a HOUSEHOLDconfiguration user interface. The CP function can be provided by acomputer running a CP application module, or by a handheld controller(e.g., the controller 708) also running a CP application module, forexample. The zone player is any other device on the network that isplaced to participate in the automatic configuration process. The ZP, asa notation used herein, includes the controller 708 or a computingdevice, for example. In some embodiments, the functionality, or certainparts of the functionality, in both the CP and the ZP are combined at asingle node (e.g., a ZP contains a CP or vice-versa).

In certain embodiments, configuration of a HOUSEHOLD involves multipleCPs and ZPs that rendezvous and establish a known configuration suchthat they can use a standard networking protocol (e.g., IP over Wired orWireless Ethernet) for communication. In an embodiment, two types ofnetworks/protocols are employed: Ethernet 802.3 and Wireless 802.11g.Interconnections between a CP and a ZP can use either of thenetworks/protocols. A device in the system as a member of a HOUSEHOLDcan connect to both networks simultaneously.

In an environment that has both networks in use, it is assumed that atleast one device in a system is connected to both as a bridging device,thus providing bridging services between wired/wireless networks forothers. The zone player 706 in FIG. 7 is shown to be connected to bothnetworks, for example. The connectivity to the network 712 is based onEthernet and/or Wireless, while the connectivity to other devices 702,704 and 708 is based on Wireless and Ethernet if so desired.

It is understood, however, that in some embodiments each zone player706, 704, 702 may access the Internet when retrieving media from thecloud (e.g., the Internet) via the bridging device. For example, zoneplayer 702 may contain a uniform resource locator (URL) that specifiesan address to a particular audio track in the cloud. Using the URL, thezone player 702 may retrieve the audio track from the cloud, andultimately play the audio out of one or more zone players.

VII. Another Example System Configuration

FIG. 8 shows a system 800 including a plurality of interconnectednetworks including a cloud-based network and at least one local playbacknetwork. A local playback network includes a plurality of playbackdevices or players, though it is understood that the playback networkmay contain only one playback device. In certain embodiments, eachplayer has an ability to retrieve its content for playback. Control andcontent retrieval can be distributed or centralized, for example. Inputcan include streaming content provider input, third party applicationinput, mobile device input, user input, and/or other playback networkinput into the cloud for local distribution and playback.

As illustrated by the example system 800 of FIG. 8, a plurality ofcontent providers 820-850 can be connected to one or more local playbacknetworks 860-870 via a cloud and/or other network 810. Using the cloud810, a multimedia audio system server 820 (e.g., Sonos™), a mobiledevice 830, a third party application 840, a content provider 850 and soon can provide multimedia content (requested or otherwise) to localplayback networks 860, 870. Within each local playback network 860, 870,a controller 862, 872 and a playback device 864, 874 can be used toplayback audio content.

VIII. Associating with Playback Queues

FIG. 9 shows an illustrative flowchart for an example method 900 toautomatically associate a playback device (e.g., zone player) with aplayback queue upon dissociation of the playback device from a group ofnetworked playback devices. FIG. 9 further shows the example method 900to include maintaining an association with multiple playback queues.

At block 902, a playback device is associated with a first playbackqueue. In some examples, the playback device is associated with thefirst playback queue when the queue is created. In other examples, thefirst playback queue is an existing playback queue with which theplayback device is associated. For example, after creation, the firstplayback queue may persist for a period of time without being associatedwith the playback device and/or any other playback devices or networkedgroups of playback devices. In some examples, the playback device playsthe audio content of the first playback queue. In such examples, thefirst playback queue may be considered an active queue of the playbackdevice.

In some embodiments, the first playback queue and/or other playbackqueues discussed herein are stored locally in memory on the playbackdevice. In other embodiments, playback queues, including the firstplayback queue, are stored remotely relative to the playback device. Forexample, the first playback queue may be stored in a cloud-based networkor on a second playback device for access by the playback device.

In some embodiments, the first playback queue and/or other playbackqueues discussed herein include information identifying one or moreitems of audio content for play by the playback device. In otherembodiments, the first playback queue includes zero items, such that thefirst playback queue has been created and is associated with theplayback device, but does not yet include information identifying audiocontent for playback. Information identifying audio content may becontinuously added to and/or removed from the first playback queueand/or other playback queues discussed herein.

At block 904, the playback device joins a group of playback devices toplay audio in synchrony. The group includes at least a second playbackdevice and in some examples, the group includes additional playbackdevices. A second playback queue, or group queue, is associated with thegroup for playback of audio content by the playback devices of thegroup. In some examples, one or more of the playback device, the secondplayback device, and/or other playback devices of the group is a bondedzone (e.g., a consolidated player, a paired player, etc.).

Upon joining the group, the playback device is associated with the groupqueue. In joining the group, the playback device plays the content ofthe group queue synchronously with the other playback devices of thegroup, including the second playback device. In some embodiments, a copyof the group queue may be stored in the memory on the playback devicesuch that the playback device plays from the local copy. In someexamples, the playback device plays content of the group queue byaccessing pointers associated with the media content. In otherembodiments, the playback device plays the content of the group queuewithout receiving a copy of the group queue. In such examples, theplayback device receives content to play from the second playback queuewithout, for example, storing a copy of the second playback queue.

As described at block 906, in some examples of the example method 900,when the playback device is linked to the group, the playback devicemaintains an association with the first playback queue while associatedwith the second playback queue (i.e., group queue). In some embodiments,the playback device maintains the first playback queue by locallystoring a copy of the first playback queue upon joining the group. Inother embodiments, the first playback queue is stored remotely and theplayback device maintains an association with the remotely stored firstplayback queue. In yet another embodiment, the playback device may savethe items of the first playback queue in the order of play at the timethe playback device joined the group or in some other configuration. Inaddition to maintaining an association with the first playback queueupon joining the group, the playback device is associated with thesecond playback queue such that the playback device is simultaneouslyassociated with both the first playback queue and the second playbackqueue.

In some embodiments, the playback device may associate with multipleplayback queues in addition to the first playback queue and the secondplayback queue while in the group, via, for example, local storage of orremote access to additional playback queues. Although the playbackdevice may associate with multiple playback queues, a particularplayback queue may be selected as the active queue for the playbackdevice. The playback device plays the audio content of the active queue.For example, as a member of the group, the playback device may play thegroup queue as the active queue. In some embodiments, a particularplayback queue is selected as the active queue by, for example,assigning the playback queue as the active queue for the playbackdevice.

At block 908, the playback device is removed from the group. Removingthe playback device from the group may involve, for example, a userinput to ungroup or remove the playback device from the group. In someexamples, the playback device leaves the group and is a stand-alonedevice not associated with any other groups. As a stand-alone device,the playback device may be a part of a bonded zone. In other examples,the playback device leaves the group and joins a different group.

Upon removal from the group, the playback device is associated with atleast one playback queue such that the playback device is enabled toplay content from the playback queue after removal from the group. Insome embodiments, the playback device is automatically directed to aplayback queue without further user input. In further embodiments, uponremoval from the group, a playback queue is automatically assigned asthe active playback queue of the playback device such that the playbackdevice plays audio content of the active playback queue. The examplemethod 900 includes removing the playback device from the group andautomatically associating the playback device with a playback queue foras long as the playback device is in the group. As such, at any time forduration in which the playback device is in the group, the playbackdevice may be ungrouped and automatically associated with a playbackqueue.

For example, at block 910 of the example method 900, a determination ismade whether to associate the playback device with the first playbackqueue upon removal from the group. As noted above at block 906, in someembodiments, the playback device maintains an association with the firstplayback queue upon joining the group, for example, by storing the firstplayback queue locally. In such examples, block 910 may involve adetermination to automatically assign the first playback queue as theactive queue for the first playback device upon removal from the group.In other examples, association between the playback device and the firstplayback queue may be removed when the playback device joins the group.In such examples, block 910 may include re-associating the playbackdevice with the first playback queue as the active queue. In the examplemethod 900, the first playback queue persists for at least as long asthe playback device is in the group such that the playback device may bere-associated with the first playback queue upon leaving the group.

At block 912, the first playback queue is automatically reinstated asthe active playback queue for the playback device. For example, theplayback device may recall a saved copy of the first playback queue andplay from the saved copy of the first playback queue. In other examples,the first playback device may point to a remotely stored first playbackqueue and play from the remotely stored first playback queue. In someexamples, the first playback queue is reinstated in the configuration inwhich the first playback queue was saved at the time the playback devicejoined the group. In other examples, the first playback queue may berecalled to play from the first item of the first playback queue. Inother examples, the first playback queue is restored to play in someother configuration.

In some embodiments, the playback device is automatically associatedwith a queue other than the first playback queue upon removal from thegroup. At block 914, a determination is made whether to associate theplayback device with the second playback queue, or the group queue, uponremoval of the playback device from the group. In some examples,although the playback device has left the group, the playback device maybe configured to continue to play the items in the group queue. Forexample, at block 916, the playback device is associated with the secondplayback queue upon removal of the playback device from the group. Theplayback device may be associated with the second playback queue byinheriting a copy of the second playback queue or remotely accessing thecontent of the second playback queue via a pointer.

In some embodiments, the second playback queue is associated with boththe group and the playback device, respectively. Further, the playbackdevice may play the audio content of the second playback queue as anactive queue independent of the group. For example, the group and theplayback device may each play the content of the second playback queuein a different order. In further embodiments, modification of the secondplayback queue by the playback device results in a new queue that isdifferent from the second playback queue associated with the group.Example modifications to the second playback queue by the playbackdevice may include content or order of play.

The playback device may be automatically associated with a thirdplayback queue that is different from the first playback queue and thesecond playback queue. At block 918, the playback device is directed toa third playback queue when the playback device is ungrouped. The thirdplayback queue may be, for example, a playback queue that has beencreated but not yet associated with a playback device. In otherexamples, the third playback queue is a playback queue that isassociated with a third playback device, multiple different playbackdevices, and/or one or more groups different from the group that theplayback device left. In other examples, the third playback queuecontains one or more items copied from one or more of the first playbackqueue, the second playback queue, or another playback queue differentfrom the first playback queue and the second playback queue.

In some examples, upon being associated with the third playback queue,the playback device plays the audio of the third playback queue. At thesame time the playback device plays the third playback queue, theplayback device may maintain an association with the first playbackqueue and/or the second playback queue, as described above (block 906).For example, the playback device may store copies of one or more of thefirst, second, or third playback queues. At a later time, the playbackdevice may be directed to play the audio content of one of the firstplayback queue, the second playback queue, or other associated playbackqueues.

As shown in FIG. 9, in some embodiments of the example method 900, thefirst playback queue maintains association with one or more playbackqueues. As further shown in FIG. 9, upon dissociation from a group, theplayback device is directed to at least one playback queue. Indetermining to which playback queue to direct the playback device uponremoval from the group, the example method 900 is not limited to thedeterminations or the order of blocks 910, 914, and/or 918 asillustrated in FIG. 9.

In operation, for example, the example method 900 provides forflexibility in moving a zone player, or other playback devices, in andout of a networked group of zone players without disrupting the abilityof the zone player to be in a play-ready state upon receiving a commandto operate. For example, a user may assign a zone player to a group toplay media content (e.g., songs) in a group queue. Subsequently, theuser may decide to remove the zone player from the group. In response toremoval of the zone player from the group, the example method 900automatically directs the zone player to a playback queue such that thezone player is continuously enabled to play items of a queue. Forexample, based on some user setting(s) or other configuration, theexample method 900 may restore an earlier playback queue with which thezone player maintained an association upon joining the group as anactive queue. Optionally, the example method 900 may provide for thezone player to be independently associated with the group queue so thatthe zone player continues to play the group queue after leaving thegroup. In some examples, the zone player may join a new group orassociate with a new queue and play the content of the new queue. Theexample method 900 enables a zone player to seamlessly move betweenoperating as part of a group or as a stand-alone device withoutdisrupting the ability of the zone player to play audio content ondemand.

FIG. 10 illustrates a flow diagram of an example method 1000 toassociate a playback device with at least one of a saved playback queueor a group queue upon dissociation of the playback device from a group.

At block 1002, the playback device is associated with a first playbackqueue. As noted above with respect to block 902 of the example method900, the first playback queue may be a previously existing playbackqueue or a playback queue created for the playback device. Further, thefirst playback queue may be stored locally on the playback device oraccessed remotely by the playback device. As described above withrespect to the example method 900, the playback device may play theaudio content of the first playback queue.

At block 1004, the playback device is linked to a group associated witha second playback queue. Upon association with the group, the playbackdevice plays the content of the second playback queue in synchronizationwith other playback devices in the group.

Although the playback device plays the second playback queue as part ofthe group, the playback device may continue to associate with the firstplayback queue. At block 1006, upon joining the group, the playbackdevice saves the first playback queue. For example, content of the firstplayback queue may be saved in an order of play as at the time theplayback device joined the group. In other examples, the playback devicesaves the first playback queue in some other configuration.

In saving the first playback queue and associating with the secondplayback queue, the playback device maintains the first playback queueand the second playback queue, as represented at block 1008. Forexample, as a member of the group, the playback device plays the contentof the second playback queue synchronously with other playback devicesin the group. Simultaneously or substantially simultaneously, theplayback device maintains an association with the first playback queueby, for example, storing a copy of the first playback queue ormaintaining a pointer to a remotely stored first playback queue.

At block 1010, the playback device is removed or dissociated from thegroup. Dissociation of the playback device from the group does notaffect the play mode of the group. In certain embodiments, the groupcontinues to play the second playback queue.

In the example method 1000, removal of the playback device from thegroup is a trigger to automatically associate or direct the playbackdevice to a playback queue to enable the playback device to access audiocontent. As described with respect to the example method 900 of FIG. 9,for as long as the playback device is in the group, the playback devicemay be removed from the group and automatically associated with aplayback queue. At block 1012, a determination is made to direct theplayback device to the first playback queue or the second playbackqueue. The determination at block 1012 may include, for example,directing the playback device to play the first playback queue as theactive queue or associating the playback device with the second playbackqueue to play the second playback queue as a stand-alone device.

At block 1014, the first playback queue is reinstated to the playbackdevice as the active queue. The order of play of the content of thefirst playback queue upon reinstatement may depend upon, for example,the manner in which the first playback queue was saved when the playbackdevice joined the group. For example, the first playback queue may berestored or recalled to the playing order of the items of the queue whenthe playback device joined the group. In other examples, uponreinstatement as the active queue, the first playback queue returns tothe first item of the queue or is configured to play in another manner.

In other examples, prior to playing the first playback queue as theactive queue, the playback device may need or want to re-associate withthe first playback queue. For example, the playback device may join thegroup, but not maintain an association with the first playback queue inthe manner described at block 1006. After leaving the group, theplayback device may re-associate with the first playback queue, therebyenabling the playback device to access the content of the first playbackqueue.

In other embodiments, upon dissociation from the group, the firstplayback queue is directed to associate with the second playback queue.At block 1016, the playback device is associated with the secondplayback queue. In some examples, the second playback queue, or thegroup queue, is selected as the active playback queue for the playbackdevice after removal from the group. In some examples, the playbackdevice may inherit or receive a copy of the second playback queue uponleaving the group such that playback device plays the second playbackqueue from the locally stored copy.

In other examples, the second playback queue may be shared betweenplayback devices or groups that are not linked. For example, the groupof the example method 1000 may include a first playback device, a secondplayback device, and a third playback device. Upon dissociation of thefirst playback device from the group, the group continues to play thesecond playback queue. The second playback queue is also associated withthe first playback device such that each of the group and the firstplayback device traverse the second playback queue independently. Forexample, the second playback device and the third playback device playthe second playback queue synchronously as part of the group. The firstplayback device also plays second playback queue. In some examples, oneor more items of the second playback queue is played in a differentorder by the first playback device and the group. In some examples, thesecond playback queue is modified by the first playback device. In suchexamples, the modified second playback queue is treated as a new queuethat is not shared with the group. In other examples, the secondplayback queue is modified by the group such that the group plays themodified second playback queue and the first playback device continuesto play the unmodified second playback queue.

In the above example, the second playback queue may be stored on thefirst playback device, the second playback device, the third playbackdevice, a cloud network, or in another location. The first playbackdevice and the group may access the second playback queue from itsstored location. Further, the second playback queue and other playbackqueues discussed herein may be stored on a playback device or networkbut, in some examples, not associated with the storage playback deviceor network.

In some embodiments of the above example, upon removal from the group,the first playback device is associated with the second playback queueand plays the second playback queue but continues to maintain anassociation with the first playback queue. In such examples, the secondplayback queue is the active queue from which the playback device playsaudio content. For example, the first playback device may play thesecond playback queue while storing the first playback queue locally. Insome examples, at a later time, the first playback device is directed toplay the first playback queue as the active queue.

At block 1018 of the example method 1000 as illustrated in FIG. 10, thesecond playback queue is selectively associated with the playback deviceas the active queue. In some embodiments, although the playback deviceis enabled to access the content of the second playback queue afterleaving the group, some user setting(s) or configuration(s) provide foraudio control with respect to whether the playback device automaticallyplays the content of the second playback queue. At block 1018, adetermination is made whether to play or to pause the audio content ofthe second playback queue upon association of the second playback queuewith the playback device.

For example, at block 1020, the second playback queue is associated withthe playback device as an active queue but the playback device isconfigured to pause audio of the second playback queue upon removal fromthe group. Play of the second playback queue by the playback device mayresume at a later time. In other examples, after leaving the group andindependently associating with the second playback queue, the playbackdevice automatically plays the second playback queue without furtheruser input, as shown at block 1022. Play of the second playback queue atblock 1022 or resumption of play at a later time at block 1020 includes,for example, playing the first item of the second playback queue,playing the item of the second playback queue that was playing when theplayback device left the group, or playing the items of the secondplayback queue in some other configuration. The determination at block1018 for the playback device to play or pause the content of the secondplayback queue does not affect the play mode of the group.

In some embodiments, a similar or substantially similar determination asdescribed at block 1018 to play or pause the content of the secondplayback queue is made at block 1014 with respect to the first playbackqueue. For example, at block 1014, the first playback queue isreinstated as the active queue of the playback device upon removal ofthe playback device from the group, but the playback device may not playthe audio content of the first playback queue until receiving furtherinput.

In operation, for example, the example method 1000 provides for a zoneplayer, or other playback device, to maintain multiple playback queuesas the zone player moves in and out of a networked group or is assignedto or shares different playback queues. A user may associate a zoneplayer operating as a stand-alone device with a first playback queue,and in some cases, the zone player may be associated with multipleplayback queues. In some examples, the zone player may play the contentof an associated queue, such as the first playback queue, as the activequeue. The user may subsequently associate the zone player to anetworked group to play a group queue. The example method 1000 providesfor the zone player to join the group without losing the first queue orpreviously associated queues. For example, the zone player may save acopy of the first queue upon joining the group or maintain associationwith a remotely stored first queue. In response to leaving the group,the zone player may automatically recall the first queue as the activequeue without the user needing to reassociate the zone player with thefirst queue. Play of the first queue may resume in the state of play aswhen the zone player joined the group, thereby providing foruninterrupted play of the first queue before and after the zone playerassociates with group.

Further, the example method 1000 provides for the zone player toautomatically associate with the group queue after the zone playerleaves the group. Further, in associating the zone player with the groupqueue, the zone player may independently play content from the groupqueue as the active queue for the zone player. For example, although auser may remove the zone player from the group, the user may wish tocontinue to play the group queue from the zone player. In the examplemethod 1000, the zone player may inherit a copy of the group queue orshare access to the group queue with the group such that the zone playerplays the group queue as an active queue without being linked to thegroup. Additionally, the user may modify the group queue with respect tothe zone player. For example, the user may create a new queue for thezone player that is at least partially based on the group queue. Theexample method 1000 provides for the zone player to maintain, forexample, the group queue, the modified grouped queue, and/or multipleother playback queues to restore or move between queues as the usercontrols the zone player within a network.

In operation, when the zone player is removed from the group, theexample method 1000 provides for the zone player to be automaticallyassociated with a playback queue, as described above. Further, inassociating with the queue, the example method 1000 provides for thezone player to automatically play the audio content of the queue withoutrequiring further user input. For example, a user may remove the zoneplayer from the group and upon leaving the group, the zone player may beautomatically directed to a saved queue. Immediately or substantiallyimmediately upon being directed to the saved queue, the zone playerbegins to play the audio content of the saved queue without requiringthe user to, for example, press a button on the zone player to commenceplay. The example method 1000 provides for the zone player to transitionbetween a group queue and another queue while providing forsubstantially continuous play of audio content by the zone player.

Additionally, the example method 1000 provides for audio control of thezone player after leaving the group in that zone player is enabled toplay a queue after leaving the group, but does not play the audiocontent until receiving further user input. For example, a user mayremove the zone player from the group and prefer for the zone player notto play audio at that time. The example method 1000 provides forassociation of the zone player with a queue to prevent the zone playerfrom having an empty playback queue upon removal from the group.Further, the example method 1000 enables the zone player to play itemsin a queue when the user wishes to resume operation of the zone player.The example method 1000 facilitates ready operation of the zone playerat the user's command.

FIG. 11 illustrates an example system 1100 for associating a playbackdevice with a playback queue upon removal of the playback device from agroup.

In FIG. 11, an example playback device 1102 is associated with aplayback queue 1112. In some examples, the playback queue 1112 is aqueue created for the playback device 1102. In other examples, theplayback device 1102 is associated with the playback queue 1112 at alater time after creation of the playback queue 1112. In some examples,the playback queue 1112 is an active queue for the playback device 1102,such that the playback device 1102 plays the content of the playbackqueue 1112.

The example playback device joins a group 1106. The group 1106 includesat least one second playback device 1104. The group 1106 is associatedwith a group queue 1116.

Upon joining the group 1106, the playback device 1102 is associated withthe group queue 1116. Further, upon joining the group, the playbackdevice 1102 plays the content of the group queue 1116. While theplayback device 1102 is in the group 1106, the playback device 1102maintains an association with the playback queue 1112. For example, theplayback device 1102 may store a copy of the playback queue 1112 orcontinue to affiliated with the playback queue 1112 via remote access toa cloud network.

In the example system 1100, the playback device 1102 leaves the group1106, in response to, for example, a user input to remove the devicefrom the group. Upon dissociation from the group, the device 1102 isassociated with a playback queue so as to avoid an empty playback queue.In the example system 1100, when the playback device 1102 is ungroupedfrom the group 1106, the playback device 1102 is automaticallyassociated with a playback queue without further user input.

For example, the playback device 1102 may be automatically directed tothe saved playback queue 1112. In such examples, the playback queue 1112is reinstated for play on the playback device 1102 as the activeplayback queue of the playback device 1102.

In other examples, upon leaving the group 1106, the playback device 1102is associated with, or inherits, the group queue 1116. For example, theplayback device 1102 may store a copy of the group queue 1116 orremotely access the group queue 1116 to play the group queue 1116separately from the group 1106.

In some examples, the second playback device 1104 continues to associatewith the playback queue 1116 after the playback device 1102 has left thegroup 1106. For example, the second playback device 1104 may remain aspart of the group 1106 with other playback devices. In other examples,the group 1106 may no longer exist after the playback device 1102 leavesthe group such that the second playback device 1104 is the only playbackdevice associated with the group queue 1116. In such examples, thesecond playback device 1104 may continue to associate with the formergroup queue 1116. In some examples, both the playback device 1102 andthe second playback device 1104 are associated with the group queue 1116and play the playback queue 1116 as active queues, but traverse theplayback queue 1116 separately.

In other examples, upon leaving the group 1106, the playback device 1102is automatically grouped with a new group 1108 including at leastplayback devices 1122, 1124. Upon joining the group 1108, the playbackdevice 1102 is associated with playback queue 1118 of the group 1108.

In other examples, the playback device 1102 is automatically associatedwith a new playback queue 1120. In some examples, the playback queue1120 is a previously established queue associated with zero or moreplayback devices. In some examples, the playback queue 1120 includesitems copied from, for example, one or more of the playback queue 1112of the playback device 1102 or the group queue 1116, or another playbackqueue different from the playback queue 1112 of the playback device 1102or the group queue 1116.

In the example system 1100, upon leaving the group 1106, the playbackdevice 1102 automatically associates with a playback queue that includeone or more items for play by the playback device 1102. Further, in theexample system 1100, the playback device 1102 may be associated withmultiple queues at any point in time. For example, the playback devicemay associate with one or more of playback queues 1112, 1116, 1118, or1120 as the playback device 1102 moves within the system 1100. Inaddition to maintaining an association with one or more of playbackqueues 1112, 1116, 1118, or 1120, the playback device 1102 may beselected to play one of the playback queues 1112, 1116, 1118, or 1120 asan active queue.

In certain embodiments, the playback device 1102 maintains at least oneplayback queue at all times such that the playback device 1112 isenabled to responsively play items in a playback queue upon receiving aninput to operate.

IX. Conclusion

The descriptions above disclose various example systems, methods,apparatus, and articles of manufacture including, among othercomponents, firmware and/or software executed on hardware. However, suchexamples are merely illustrative and should not be considered aslimiting. For example, it is contemplated that any or all of thesefirmware, hardware, and/or software components can be embodiedexclusively in hardware, exclusively in software, exclusively infirmware, or in any combination of hardware, software, and/or firmware.Accordingly, while the following describes example systems, methods,apparatus, and/or articles of manufacture, the examples provided are notthe only way(s) to implement such systems, methods, apparatus, and/orarticles of manufacture.

Certain embodiments disclosed herein provide a method includingreceiving a first command by a device to group a first playback devicewith at least a second playback device for synchronous audio playback.In the example method, the group is associated with a first playbackqueue. The first playback queue comprises a list of one or more itemsfor playback by the group. The example method includes, for as long asthe playback device is in the group, receiving a second command by thedevice to remove the first playback device from the group, wherein thefirst playback device is ungrouped and automatically associated with asecond playback queue. In the example method, the second playback queuecomprises a list of one or more items for playback by the playbackdevice.

Certain embodiments provide an example playback device comprising aprocessor configured to group the playback device with at least a secondplayback device for synchronous audio playback. The group is associatedwith a first playback queue comprising a list of one or more items forplayback by the group. The processor is configured, for as long as theplayback device is in the group, to remove the playback device from thegroup. The first playback device is ungrouped and automaticallyassociated with a second playback queue. The second playback queuecomprises a list of one or more items for playback by the playbackdevice.

Certain embodiments provide a non-transitory computer-readable storagemedium including a computer program which, when executed by a processor,implements at least a method. The example method includes receiving afirst command by a device to group a first playback device with at leasta second playback device for synchronous audio playback. In the examplemethod, the group is associated with a first playback queue. The firstplayback queue comprises a list of one or more items for playback by thegroup. The example method includes, for as long as the playback deviceis in the group, receiving a second command by the device to remove thefirst playback device from the group, wherein the first playback deviceis ungrouped and automatically associated with a second playback queue.In the example method, the second playback queue comprises a list of oneor more items for playback by the playback device.

Additionally, references herein to “embodiment” means that a particularfeature, structure, or characteristic described in connection with theembodiment can be included in at least one example embodiment of theinvention. The appearances of this phrase in various places in thespecification are not necessarily all referring to the same embodiment,nor are separate or alternative embodiments mutually exclusive of otherembodiments. As such, the embodiments described herein, explicitly andimplicitly understood by one skilled in the art, can be combined withother embodiments.

The specification is presented largely in terms of illustrativeenvironments, systems, procedures, steps, logic blocks, processing, andother symbolic representations that directly or indirectly resemble theoperations of data processing devices coupled to networks. These processdescriptions and representations are typically used by those skilled inthe art to most effectively convey the substance of their work to othersskilled in the art. Numerous specific details are set forth to provide athorough understanding of the present disclosure. However, it isunderstood to those skilled in the art that certain embodiments of thepresent disclosure can be practiced without certain, specific details.In other instances, well known methods, procedures, components, andcircuitry have not been described in detail to avoid unnecessarilyobscuring aspects of the embodiments. Accordingly, the scope of thepresent disclosure is defined by the appended claims rather than theforgoing description of embodiments.

When any of the appended claims are read to cover a purely softwareand/or firmware implementation, at least one of the elements in at leastone example is hereby expressly defined to include a tangible mediumsuch as a memory, DVD, CD, Blu-ray, and so on, storing the softwareand/or firmware.

We claim:
 1. A first playback device comprising: at least one processor;a non-transitory computer-readable medium; and program instructionsstored on the non-transitory computer-readable medium that, whenexecuted by the at least one processor, cause the first playback deviceto perform functions comprising: while in a media playback systemcomprising a plurality of playback devices, receiving a first request toassociate with a first playback queue that is stored remotely from, andpersists unassociated with, any playback device of the media playbacksystem; after receiving the first request: associating with the firstplayback queue; and designating the first playback queue as an activequeue of the first playback device: after associating with the first,playback queue, receiving a second request to enter into a group with asecond playback device that is associated with a second playback queue;after receiving the second request: entering into the group with thesecond playback device such that the first playback device is configuredto receive (i) audio content and (ii) timing information from the secondplayback device such that the first playback device is configured toplay back audio content in synchrony with the second playback device;associating with the second playback queue; maintaining an associationwith the first playback queue after entering into the group with thesecond playback device and after associating with the second playbackqueue; designating the second playback queue as the active queue of thefirst playback device; and de-designating the first playback queue asthe active queue of the first playback device; receiving a third requestto leave the group with the second playback device; and after receivingthe third request, de-designating the second playback queue as itsactive queue.
 2. The first playback device of claim 1, whereinde-designating the second playback queue as its active queue furthercomprises disassociating from the second playback queue.
 3. The firstplayback device of claim 1, further comprising program instructionsstored on the non-transitory computer-readable medium that, whenexecuted by the at least one processor, cause the first playback deviceto perform functions comprising: after de-designating the secondplayback queue as the active queue of the first playback device,re-designating the first playback queue as the active queue of the firstplayback device.
 4. The first playback device of claim 1, wherein thethird request to leave the group with the second playback device furthercomprises a request to enter into a group with a third playback devicethat is associated with a third playback queue.
 5. The first playbackdevice of claim 4, further comprising program instructions stored on thenon-transitory computer-readable medium that, when executed by the atleast one processor, cause the first playback device to performfunctions comprising: after receiving the third request: entering intothe group with the third playback device such that the first playbackdevice is configured to receive (i) audio content and (ii) timinginformation from the third playback device such that the first playbackdevice is configured to play back audio content in synchrony with thethird playback device; associating with the third playback queue;maintaining an association with the first playback queue after enteringinto the group with the third playback device and after associating withthe third playback queue; and designating the third playback queue asthe active queue of the first playback device.
 6. A non-transitorycomputer-readable medium having stored thereon program instructionsthat, when executed by at least one processor, cause a first playbackdevice to perform functions comprising: while in a media playback systemcomprising a plurality of playback devices, receiving a first request toassociate with a first playback queue that is stored remotely from, andpersists unassociated with, any playback device of the media playbacksystem; after receiving the first request: associating with the firstplayback queue; and designating the first playback queue as an activequeue of the first playback device; after associating with the firstplayback queue, receiving a second request to enter into a group with asecond playback device that is associated with a second playback queue;after receiving the second request: entering into the group with thesecond playback device such that the first playback device is configuredto receive (i) audio content and (ii) timing information from the secondplayback device such that the first playback device is configured toplay back audio content in synchrony with the second playback device;associating with the second playback queue; maintaining an associationwith the first playback queue after entering into the group with thesecond playback device and after associating with the second playbackqueue; designating the second playback queue as the active queue of thefirst playback device; and de-designating the first playback queue asthe active queue of the first playback device; receiving a third requestto leave the group with the second playback device; and after receivingthe third request, de-designating the second playback queue as itsactive queue.
 7. The non-transitory computer-readable medium of claim 6,wherein de-designating the second playback queue as its active queuefurther comprises disassociating from the second playback queue.
 8. Thenon-transitory computer-readable medium of claim 6, further comprisingprogram instructions stored thereon that, when executed by the at leastone processor, cause the first playback device to perform functionscomprising: after de-designating the second playback queue as the activequeue of the first playback device, re-designating the first playbackqueue as the active queue of the first playback device.
 9. Thenon-transitory computer-readable medium of claim 6, wherein the thirdrequest to leave the group with the second playback device furthercomprises a request to enter into a group with a third playback devicethat is associated with a third playback queue.
 10. The non-transitorycomputer-readable medium of claim 9, further comprising programinstructions stored thereon that, when executed by the at least oneprocessor, cause the first playback device to perform functionscomprising: after receiving the third request: entering into the groupwith the third playback device such that the first playback device isconfigured to receive (i) audio content and (ii) timing information fromthe third playback device such that the first playback device isconfigured to play back audio content in synchrony with the thirdplayback device; associating with the third playback queue; maintainingan association with the first playback queue after entering into thegroup with the third playback device and after associating with thethird playback queue; and designating the third playback queue as theactive queue of the first playback device.
 11. A method comprising:while in a media playback system comprising a plurality of playbackdevices, receiving, by a first playback device, a first request toassociate with a first playback queue that is stored remotely from, andpersists unassociated with, any playback device of the media playbacksystem; after receiving the first request: associating with the firstplayback queue; and designating the first playback queue as an activequeue of the first playback device: after associating with the firstplayback queue, receiving, by the first playback device, a secondrequest to enter into a group with a second playback device that isassociated with a second playback queue; after receiving the secondrequest: entering into the group with the second playback device suchthat the first playback device is configured to receive (i) audiocontent and (ii) timing information from the second playback device suchthat the first playback device is configured to play back audio contentin synchrony with the second playback device; associating with thesecond playback queue; maintaining an association with the firstplayback queue after entering into the group with the second playbackdevice and after associating with the second playback queue; designatingthe second playback queue as the active queue of the first playbackdevice; and de-designating the first playback queue as the active queueof the first playback device; receiving, by the first playback device, athird request to leave the group with the second playback device; andafter receiving the third request, de-designating the second playbackqueue as its active queue.
 12. The method of claim 11, furthercomprising: after de-designating the second playback queue as the activequeue of the first playback device, re-designating the first playbackqueue as the active queue of the first playback device.
 13. The methodof claim 11, wherein de-designating the second playback queue as itsactive queue further comprises disassociating from the second playbackqueue.
 14. The method of claim 11, wherein the third request to leavethe group with the second playback device further comprises a request toenter into a group with a third playback device that is associated witha third playback queue.
 15. The method of claim 14, further comprising:after receiving the third request: entering into the group with thethird playback device such that the first playback device is configuredto receive (i) audio content and (ii) timing information from the thirdplayback device such that the first playback device is configured toplay back audio content in, synchrony with the third playback device;associating with the third playback queue; maintaining an associationwith the first playback queue after entering into the group with thethird playback device and after associating with the third playbackqueue; and designating the third playback queue as the active queue ofthe first playback device.